concurrent patterns : parallels in system and language design

[email protected] c o n c u r r e n c y a n d pa r a l l e l i s m a r e usually discussed together, and they are both important in reorganizing a program for execution on multiple cores or multiple computers. Parallelism asks, “How can we break a program up into independently executing parts?” It is very much in the domain of compiler writers and library providers, as the necessary program transformations are tedious at best. Concurrency asks, “How can independent programs share a value once in a while?” It bedevils program designers at every level—providers of parallelism toolkits, operating systems designers, application programmers, system administrators providing distributed network services, and even folks just trying to sell a few books.